Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a0673da45787b8ec8af452ed74e044428a16172c1e4635a874d326a6151385e

Tx prefix hash: ea16a7875b87ee1158bfbcb1ecaa15c599e965c9098bf17795616761516cfe4c
Tx public key: 1b65e3dd1eea2a24114d2932a27b22f698fa2d6b82dcbbec40fdc4a5e53bc84e
Timestamp: 1715760975 Timestamp [UCT]: 2024-05-15 08:16:15 Age [y:d:h:m:s]: 01:029:22:40:46
Block: 1022415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282257 RingCT/type: yes/0
Extra: 011b65e3dd1eea2a24114d2932a27b22f698fa2d6b82dcbbec40fdc4a5e53bc84e0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91db8cc18527e538911e6bfe2b4a9bbb32765713146a641aa77fdb3d0ce40917 0.600000000000 1487010 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": 1022425, "vin": [ { "gen": { "height": 1022415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91db8cc18527e538911e6bfe2b4a9bbb32765713146a641aa77fdb3d0ce40917" } } ], "extra": [ 1, 27, 101, 227, 221, 30, 234, 42, 36, 17, 77, 41, 50, 162, 123, 34, 246, 152, 250, 45, 107, 130, 220, 187, 236, 64, 253, 196, 165, 229, 59, 200, 78, 2, 17, 0, 0, 0, 3, 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