Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 685c6d44443a9b0d64f48bb6339f9314c75962cde60973b2f748a050becd2723

Tx prefix hash: 227ce96392c17fd694c8c4250fe651c28835f71c8114d8bc24e67b34b4683f6d
Tx public key: 1244a1dd55f656cb5ae804a8491e10b18455cd1e172b2afd7493904838329793
Timestamp: 1701345049 Timestamp [UCT]: 2023-11-30 11:50:49 Age [y:d:h:m:s]: 01:182:16:19:54
Block: 902880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391784 RingCT/type: yes/0
Extra: 011244a1dd55f656cb5ae804a8491e10b18455cd1e172b2afd7493904838329793021100000004faf35c9c000000000000000000

1 output(s) for total of 0.625725330000 dcy

stealth address amount amount idx
00: 2ea45bb0d184ad7b8535b44c68f36ecc7e0ac0697f9741bc64b52f5d6a7e82d8 0.625725330000 1359543 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 902890, "vin": [ { "gen": { "height": 902880 } } ], "vout": [ { "amount": 625725330, "target": { "key": "2ea45bb0d184ad7b8535b44c68f36ecc7e0ac0697f9741bc64b52f5d6a7e82d8" } } ], "extra": [ 1, 18, 68, 161, 221, 85, 246, 86, 203, 90, 232, 4, 168, 73, 30, 16, 177, 132, 85, 205, 30, 23, 43, 42, 253, 116, 147, 144, 72, 56, 50, 151, 147, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8