Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a757485d3e1f94e6840bcaa5e5f00efae14d06687e28a365c618950f29add684

Tx prefix hash: cf184f735b314137a3fc1545df32fdc9d4432dea44ccb3f4cce9a7ee20f5a905
Tx public key: 8f242797ddf475913e3aef51de555deb76d5d7f8f0b8a94fd5d2dcb20dbbe6bd
Timestamp: 1639268102 Timestamp [UCT]: 2021-12-12 00:15:02 Age [y:d:h:m:s]: 03:324:20:54:34
Block: 393533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1008653 RingCT/type: yes/0
Extra: 018f242797ddf475913e3aef51de555deb76d5d7f8f0b8a94fd5d2dcb20dbbe6bd0211000000020eb261b4000000000000000000

1 output(s) for total of 30.490743223000 dcy

stealth address amount amount idx
00: f9afcec76b970a334f6dae64e93a9bb06e0145e1da42976d1b7176501175b27b 30.490743223000 790804 of 0

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": 393543, "vin": [ { "gen": { "height": 393533 } } ], "vout": [ { "amount": 30490743223, "target": { "key": "f9afcec76b970a334f6dae64e93a9bb06e0145e1da42976d1b7176501175b27b" } } ], "extra": [ 1, 143, 36, 39, 151, 221, 244, 117, 145, 62, 58, 239, 81, 222, 85, 93, 235, 118, 213, 215, 248, 240, 184, 169, 79, 213, 210, 220, 178, 13, 187, 230, 189, 2, 17, 0, 0, 0, 2, 14, 178, 97, 180, 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