Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b79ade1234abf3038dd56014a8fbbed6d0c7f5b535712266913f1f2918b23cd

Tx prefix hash: da14d934828e4aa15b5b15689308b91b1c134dfe03e34c587cd34b3d89374ec0
Tx public key: 8251822a3a98c90ca448b4cba3fc9914ecd3a7ab148a3883b4c1f175d091b23d
Timestamp: 1701329416 Timestamp [UCT]: 2023-11-30 07:30:16 Age [y:d:h:m:s]: 01:165:05:37:25
Block: 902757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379279 RingCT/type: yes/0
Extra: 018251822a3a98c90ca448b4cba3fc9914ecd3a7ab148a3883b4c1f175d091b23d021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.626312798000 dcy

stealth address amount amount idx
00: 2ff61c0a1fe4565b68d9aca438e0a4381d00462b0461c98a974043fe539b545c 0.626312798000 1359412 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": 902767, "vin": [ { "gen": { "height": 902757 } } ], "vout": [ { "amount": 626312798, "target": { "key": "2ff61c0a1fe4565b68d9aca438e0a4381d00462b0461c98a974043fe539b545c" } } ], "extra": [ 1, 130, 81, 130, 42, 58, 152, 201, 12, 164, 72, 180, 203, 163, 252, 153, 20, 236, 211, 167, 171, 20, 138, 56, 131, 180, 193, 241, 117, 208, 145, 178, 61, 2, 17, 0, 0, 0, 7, 230, 210, 127, 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