Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 060a7cce11e5a2363af3c6542deec6e2d087777d83a48e65474400798ea1bb74

Tx prefix hash: 753a667e62dbe89e3168e67f3d83a1cd9b6aac0cd4f7772fbe5446582d1751a9
Tx public key: 9f131e4c5c1a4822c0a9e5682b46fb2d66a2ee2391dabe87e9872bbcffb13653
Timestamp: 1710140033 Timestamp [UCT]: 2024-03-11 06:53:53 Age [y:d:h:m:s]: 01:029:22:42:01
Block: 975823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282389 RingCT/type: yes/0
Extra: 019f131e4c5c1a4822c0a9e5682b46fb2d66a2ee2391dabe87e9872bbcffb1365302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bad4602610954ae5d2142b93f83a67ba7db3c343596ce03fa4e9458db9f4529b 0.600000000000 1435798 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": 975833, "vin": [ { "gen": { "height": 975823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bad4602610954ae5d2142b93f83a67ba7db3c343596ce03fa4e9458db9f4529b" } } ], "extra": [ 1, 159, 19, 30, 76, 92, 26, 72, 34, 192, 169, 229, 104, 43, 70, 251, 45, 102, 162, 238, 35, 145, 218, 190, 135, 233, 135, 43, 188, 255, 177, 54, 83, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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