Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da00c0daab9a3a6212e1e2cc6d42696f9e66ce1d26b5c52b3dad859b756fbc9a

Tx prefix hash: 407b2bf6c41590578410d5d475160c5b5743498b85813e8259fba3cea1c88d92
Tx public key: 28c61f82844c177808fb95d9ef32a281f43e600968671f75fef59640c42ee2f3
Timestamp: 1722344329 Timestamp [UCT]: 2024-07-30 12:58:49 Age [y:d:h:m:s]: 00:326:13:36:13
Block: 1076989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233165 RingCT/type: yes/0
Extra: 0128c61f82844c177808fb95d9ef32a281f43e600968671f75fef59640c42ee2f302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfe06409f64c3794e7ca2a45e3e5e32e2e3b6c6a2e67126e95b53aadd759312a 0.600000000000 1549532 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": 1076999, "vin": [ { "gen": { "height": 1076989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfe06409f64c3794e7ca2a45e3e5e32e2e3b6c6a2e67126e95b53aadd759312a" } } ], "extra": [ 1, 40, 198, 31, 130, 132, 76, 23, 120, 8, 251, 149, 217, 239, 50, 162, 129, 244, 62, 96, 9, 104, 103, 31, 117, 254, 245, 150, 64, 196, 46, 226, 243, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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