Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55192daa36ba727bd00d1f9f8e8250cf30b2b070e2291085c14aeabd4cf42244

Tx prefix hash: c90a6db3ffb4c945f96ba5ef10ec4f14292de5f774a9423015fbeebbd283c7be
Tx public key: 7ecf77631f30bd8015314276b1b4e7bf9496e362e8b14e9264240cbf22a5c28f
Timestamp: 1735060161 Timestamp [UCT]: 2024-12-24 17:09:21 Age [y:d:h:m:s]: 01:013:22:43:44
Block: 1182309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268412 RingCT/type: yes/0
Extra: 017ecf77631f30bd8015314276b1b4e7bf9496e362e8b14e9264240cbf22a5c28f0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99207fc8f589932f9d8697d26e05d14d952299fe6fd67a7d0e8f4ba605d46870 0.600000000000 1668742 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": 1182319, "vin": [ { "gen": { "height": 1182309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99207fc8f589932f9d8697d26e05d14d952299fe6fd67a7d0e8f4ba605d46870" } } ], "extra": [ 1, 126, 207, 119, 99, 31, 48, 189, 128, 21, 49, 66, 118, 177, 180, 231, 191, 148, 150, 227, 98, 232, 177, 78, 146, 100, 36, 12, 191, 34, 165, 194, 143, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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