Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dac5a9cf676f9012a463ffb2c21bc5a3f97fcbc5433c508e0421927d1702c4af

Tx prefix hash: b972cbf0b691ea8f72d176d8777abac2ce4724c93fe45787a801547be88986d1
Tx public key: 3e2bcc29a43e553ef9f06bb2b1346701dc49dc1c4ccd2391ab76f979b0282fff
Timestamp: 1704342207 Timestamp [UCT]: 2024-01-04 04:23:27 Age [y:d:h:m:s]: 01:098:18:30:59
Block: 927745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331701 RingCT/type: yes/0
Extra: 013e2bcc29a43e553ef9f06bb2b1346701dc49dc1c4ccd2391ab76f979b0282fff02110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c970916fbf1f0acc19ebe02027e464d51d2d9a06471ae3a189e78ae84bfad2c 0.600000000000 1385581 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": 927755, "vin": [ { "gen": { "height": 927745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c970916fbf1f0acc19ebe02027e464d51d2d9a06471ae3a189e78ae84bfad2c" } } ], "extra": [ 1, 62, 43, 204, 41, 164, 62, 85, 62, 249, 240, 107, 178, 177, 52, 103, 1, 220, 73, 220, 28, 76, 205, 35, 145, 171, 118, 249, 121, 176, 40, 47, 255, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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