Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9c7089c0d45d5efa74634c5a00130cae39d5c9c0da31082033fa1a710aaf889

Tx prefix hash: 3f12252356686a91611ec6e714948dacb1283c83df672ec9747c9d20a42c5a43
Tx public key: c9827007fc6a89363e8ed1ef510c874dd7df92b2213b527dea7755b2abd6bbf3
Timestamp: 1724043012 Timestamp [UCT]: 2024-08-19 04:50:12 Age [y:d:h:m:s]: 00:164:21:23:48
Block: 1091087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117677 RingCT/type: yes/0
Extra: 01c9827007fc6a89363e8ed1ef510c874dd7df92b2213b527dea7755b2abd6bbf302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35030940609dc5dbeea9174483b38bf2b05ad0517ca8ad7eaa43a80069c4ac0c 0.600000000000 1565712 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": 1091097, "vin": [ { "gen": { "height": 1091087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35030940609dc5dbeea9174483b38bf2b05ad0517ca8ad7eaa43a80069c4ac0c" } } ], "extra": [ 1, 201, 130, 112, 7, 252, 106, 137, 54, 62, 142, 209, 239, 81, 12, 135, 77, 215, 223, 146, 178, 33, 59, 82, 125, 234, 119, 85, 178, 171, 214, 187, 243, 2, 17, 0, 0, 0, 1, 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