Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f60eda5f2b13f24b9db643c894daf6c9a2f161c6a95557b9b21f9196a04c81f

Tx prefix hash: dd40079272d65b485049b82600bd6b99bb924309890fe9fed28a016d6524b113
Tx public key: 61f3529a1e134eae7c0dd6a53ceb0e91755eeca44a0011948cb1f01a573fde2d
Timestamp: 1719578870 Timestamp [UCT]: 2024-06-28 12:47:50 Age [y:d:h:m:s]: 00:297:21:42:40
Block: 1054062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212877 RingCT/type: yes/0
Extra: 0161f3529a1e134eae7c0dd6a53ceb0e91755eeca44a0011948cb1f01a573fde2d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 372cec3b4080d8d4f2907f43e8ba66d949f602e6f0510aa90ec4173cae732bc5 0.600000000000 1524421 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": 1054072, "vin": [ { "gen": { "height": 1054062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "372cec3b4080d8d4f2907f43e8ba66d949f602e6f0510aa90ec4173cae732bc5" } } ], "extra": [ 1, 97, 243, 82, 154, 30, 19, 78, 174, 124, 13, 214, 165, 60, 235, 14, 145, 117, 94, 236, 164, 74, 0, 17, 148, 140, 177, 240, 26, 87, 63, 222, 45, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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