Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e735e7e2cfc499b8f1ee21ea555fdb6d3f2438d21fff6a5e6e5851d84225596f

Tx prefix hash: a494e31701fac7928fd4c4ba3baef06b1e027fd2dc69f9241cf146d54143ee05
Tx public key: b8b2ac64ef86c8ec66a1408e147b1abfff70faa405b186103c6f174497222a2b
Timestamp: 1709471866 Timestamp [UCT]: 2024-03-03 13:17:46 Age [y:d:h:m:s]: 01:039:21:31:13
Block: 970280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289511 RingCT/type: yes/0
Extra: 01b8b2ac64ef86c8ec66a1408e147b1abfff70faa405b186103c6f174497222a2b02110000000149a185bb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b9f0f4e7b33d859b40f23ed979ca47e1a5ea71bfafbbc59b6a3aca83bda9bec 0.600000000000 1430131 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": 970290, "vin": [ { "gen": { "height": 970280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b9f0f4e7b33d859b40f23ed979ca47e1a5ea71bfafbbc59b6a3aca83bda9bec" } } ], "extra": [ 1, 184, 178, 172, 100, 239, 134, 200, 236, 102, 161, 64, 142, 20, 123, 26, 191, 255, 112, 250, 164, 5, 177, 134, 16, 60, 111, 23, 68, 151, 34, 42, 43, 2, 17, 0, 0, 0, 1, 73, 161, 133, 187, 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