Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 379918124b4f0a7ba04912b77c449fa2c057cb551481b26caa660df410a609c9

Tx prefix hash: ad3a7375e575e465971c7afa820465bbf77bd0dc376ee91f17cc334f39820b72
Tx public key: 7a5e689e29e951ffc22c6fa3b04c1cf6edb11afd5c9ccc54ce225dac00ce9e4e
Timestamp: 1713402779 Timestamp [UCT]: 2024-04-18 01:12:59 Age [y:d:h:m:s]: 01:041:02:19:49
Block: 1002842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290374 RingCT/type: yes/0
Extra: 017a5e689e29e951ffc22c6fa3b04c1cf6edb11afd5c9ccc54ce225dac00ce9e4e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46b0cd2823d18ea07cda9a267325c29e365f86f1e37fd98fa314fe438913d357 0.600000000000 1463370 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": 1002852, "vin": [ { "gen": { "height": 1002842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46b0cd2823d18ea07cda9a267325c29e365f86f1e37fd98fa314fe438913d357" } } ], "extra": [ 1, 122, 94, 104, 158, 41, 233, 81, 255, 194, 44, 111, 163, 176, 76, 28, 246, 237, 177, 26, 253, 92, 156, 204, 84, 206, 34, 93, 172, 0, 206, 158, 78, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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