Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 607a33b5f9aabced0cba87592c2dd113ea549a475897a4e25fa7c1ab3ebade52

Tx prefix hash: f79e0637e57b725e7c7b94ee77245cbf110bd9c6708904e920c0557891814b8f
Tx public key: f85baeb71fa090b0d23d79c5334cc8cab95aae7664cc00d06e4b73e3e79697ec
Timestamp: 1702715338 Timestamp [UCT]: 2023-12-16 08:28:58 Age [y:d:h:m:s]: 01:182:13:19:48
Block: 914259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391547 RingCT/type: yes/0
Extra: 01f85baeb71fa090b0d23d79c5334cc8cab95aae7664cc00d06e4b73e3e79697ec02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa3a178deb7b8a4e7d9f9abd77438e8136b1d8c03b9dd4293afc53598b8ed1aa 0.600000000000 1371545 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": 914269, "vin": [ { "gen": { "height": 914259 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa3a178deb7b8a4e7d9f9abd77438e8136b1d8c03b9dd4293afc53598b8ed1aa" } } ], "extra": [ 1, 248, 91, 174, 183, 31, 160, 144, 176, 210, 61, 121, 197, 51, 76, 200, 202, 185, 90, 174, 118, 100, 204, 0, 208, 110, 75, 115, 227, 231, 150, 151, 236, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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