Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e305f2184a6797c7c9a02d5a1b3e88e5ee72d700d95454de7298723db3875f5

Tx prefix hash: 691467f1b651e5c46fd3c1a79d366e2789c4f1a32ba0dcb4efe75cc64cbaec23
Tx public key: acb46e4363b85a44c32943a46c5df622c4ece0e3faec1a645ad1d836fadc58f2
Timestamp: 1736218076 Timestamp [UCT]: 2025-01-07 02:47:56 Age [y:d:h:m:s]: 00:098:02:01:37
Block: 1191871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69892 RingCT/type: yes/0
Extra: 01acb46e4363b85a44c32943a46c5df622c4ece0e3faec1a645ad1d836fadc58f2021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7affb6fd48d6590d548e276a230a77066991097c4869ad64b560da4300e49f1a 0.600000000000 1678414 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": 1191881, "vin": [ { "gen": { "height": 1191871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7affb6fd48d6590d548e276a230a77066991097c4869ad64b560da4300e49f1a" } } ], "extra": [ 1, 172, 180, 110, 67, 99, 184, 90, 68, 195, 41, 67, 164, 108, 93, 246, 34, 196, 236, 224, 227, 250, 236, 26, 100, 90, 209, 216, 54, 250, 220, 88, 242, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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