Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cfdfbd972f09e36aa5664d4d6d00105f61e475d8b948fa2661e3cb9589874a9

Tx prefix hash: 774c14d5d35ea1ca1d491f2c3c53dc6aa90fc7570549c6b26f656b24c294b695
Tx public key: 84473219740b1d7f924018d1653313d075dc176f95982cf45f617431c75f9b77
Timestamp: 1730897347 Timestamp [UCT]: 2024-11-06 12:49:07 Age [y:d:h:m:s]: 00:151:02:45:51
Block: 1147814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107821 RingCT/type: yes/0
Extra: 0184473219740b1d7f924018d1653313d075dc176f95982cf45f617431c75f9b77021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61cc8ad496d6c08a0f1b044bc8b04e006350f6e875d3891493ac2c052ad748ca 0.600000000000 1632515 of 15

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": 1147824, "vin": [ { "gen": { "height": 1147814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61cc8ad496d6c08a0f1b044bc8b04e006350f6e875d3891493ac2c052ad748ca" } } ], "extra": [ 1, 132, 71, 50, 25, 116, 11, 29, 127, 146, 64, 24, 209, 101, 51, 19, 208, 117, 220, 23, 111, 149, 152, 44, 244, 95, 97, 116, 49, 199, 95, 155, 119, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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