Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7851ddcbfc4732e1e21dbe2cdbdbdbf0766ce137d03ecabcc71df9a75ed09e5f

Tx prefix hash: 4e4567b7d2e400654f4f5d262b0428cf88354ea9078b222800e5fdca42b73bd2
Tx public key: d345a42d2344d95fb3f8e32a45c4348179b5f98bf58a5515d8f63bf90a041325
Timestamp: 1728977441 Timestamp [UCT]: 2024-10-15 07:30:41 Age [y:d:h:m:s]: 00:040:08:32:42
Block: 1131986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28810 RingCT/type: yes/0
Extra: 01d345a42d2344d95fb3f8e32a45c4348179b5f98bf58a5515d8f63bf90a04132502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b42fd8fae3c2cab831dd604715bc809b90617b49459548c96256e4462afc893a 0.600000000000 1614895 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": 1131996, "vin": [ { "gen": { "height": 1131986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b42fd8fae3c2cab831dd604715bc809b90617b49459548c96256e4462afc893a" } } ], "extra": [ 1, 211, 69, 164, 45, 35, 68, 217, 95, 179, 248, 227, 42, 69, 196, 52, 129, 121, 181, 249, 139, 245, 138, 85, 21, 216, 246, 59, 249, 10, 4, 19, 37, 2, 17, 0, 0, 0, 5, 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