Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7429596974b584e11062d33b008398a35fbda338535a0566e1469b1c27bca507

Tx prefix hash: 7a61940fc63d70d26626b6d734a3b812fb30924fe80287b36ec28f9a3133c284
Tx public key: e37bc583586c9efeb6f0284d843a002d07b9b021e189c6e0b405757e6a5d8101
Timestamp: 1728591502 Timestamp [UCT]: 2024-10-10 20:18:22 Age [y:d:h:m:s]: 00:182:05:38:00
Block: 1128789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130026 RingCT/type: yes/0
Extra: 01e37bc583586c9efeb6f0284d843a002d07b9b021e189c6e0b405757e6a5d810102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d0e36a76701be1301e5df451c74807487341a4369d34112c47358f3f2de9934 0.600000000000 1611612 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": 1128799, "vin": [ { "gen": { "height": 1128789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d0e36a76701be1301e5df451c74807487341a4369d34112c47358f3f2de9934" } } ], "extra": [ 1, 227, 123, 197, 131, 88, 108, 158, 254, 182, 240, 40, 77, 132, 58, 0, 45, 7, 185, 176, 33, 225, 137, 198, 224, 180, 5, 117, 126, 106, 93, 129, 1, 2, 17, 0, 0, 0, 3, 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