Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbed70dab2fdf36a6d69420ec5fdeedc3b4aefa40298aa682e41d91e3f991153

Tx prefix hash: c39634b58597666e1977b08a01f2d0ba454b586641498aadf1701bfb4bf5f3be
Tx public key: 514d1ae8113ec6f63e72a6fb7e3e1955ab7b7e3e2d88668cd89d1f91b1d0866f
Timestamp: 1717726312 Timestamp [UCT]: 2024-06-07 02:11:52 Age [y:d:h:m:s]: 00:208:13:43:39
Block: 1038707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149265 RingCT/type: yes/0
Extra: 01514d1ae8113ec6f63e72a6fb7e3e1955ab7b7e3e2d88668cd89d1f91b1d0866f02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37d15e71ce628c56edcdbc168fae75383d45524f2e1a300f718868dfb780d137 0.600000000000 1507268 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": 1038717, "vin": [ { "gen": { "height": 1038707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37d15e71ce628c56edcdbc168fae75383d45524f2e1a300f718868dfb780d137" } } ], "extra": [ 1, 81, 77, 26, 232, 17, 62, 198, 246, 62, 114, 166, 251, 126, 62, 25, 85, 171, 123, 126, 62, 45, 136, 102, 140, 216, 157, 31, 145, 177, 208, 134, 111, 2, 17, 0, 0, 0, 4, 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