Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a75aff96f8f72fbc3da220a7466c65cb9ea54f9bdc1b0597d8920907eeabd5de

Tx prefix hash: d48cf9a6adcd7df1336af9b9d68562b12f0269f762888631526f5540ae020e61
Tx public key: 503a31836fd2bb1ae72f73e81fa142ee8634d981e2542f4cd77e69733b49df3a
Timestamp: 1715790475 Timestamp [UCT]: 2024-05-15 16:27:55 Age [y:d:h:m:s]: 00:220:13:57:08
Block: 1022654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157915 RingCT/type: yes/0
Extra: 01503a31836fd2bb1ae72f73e81fa142ee8634d981e2542f4cd77e69733b49df3a0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c39d5cee049c39f3e8e8096092b7a95d1ae9407f8a0ca5795eef171f274c742 0.600000000000 1487323 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": 1022664, "vin": [ { "gen": { "height": 1022654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c39d5cee049c39f3e8e8096092b7a95d1ae9407f8a0ca5795eef171f274c742" } } ], "extra": [ 1, 80, 58, 49, 131, 111, 210, 187, 26, 231, 47, 115, 232, 31, 161, 66, 238, 134, 52, 217, 129, 226, 84, 47, 76, 215, 126, 105, 115, 59, 73, 223, 58, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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