Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 680a22a4ce1c72d5a8726b8a21d6859e8885fd01ed884f7ec6f8b01c78b94480

Tx prefix hash: 7f49afb971de82ac7deae52cefe083e8449ac606de13dbedab2903c67f61967c
Tx public key: 42e89bbf756245c0cc981a9c63aa71cc2d9b3618d64a6f7294071f1247846af7
Timestamp: 1736572625 Timestamp [UCT]: 2025-01-11 05:17:05 Age [y:d:h:m:s]: 00:160:11:47:06
Block: 1194809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114375 RingCT/type: yes/0
Extra: 0142e89bbf756245c0cc981a9c63aa71cc2d9b3618d64a6f7294071f1247846af7021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd254bd5afeae7cbfd481c96f00df5ad00b8ecb337ed0d1ecb2c1e9e860effae 0.600000000000 1681386 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": 1194819, "vin": [ { "gen": { "height": 1194809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd254bd5afeae7cbfd481c96f00df5ad00b8ecb337ed0d1ecb2c1e9e860effae" } } ], "extra": [ 1, 66, 232, 155, 191, 117, 98, 69, 192, 204, 152, 26, 156, 99, 170, 113, 204, 45, 155, 54, 24, 214, 74, 111, 114, 148, 7, 31, 18, 71, 132, 106, 247, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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