Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4c7e1f774068e69eb72fb2ddfa7dccc7994558c4ff13b7030d23faf21f3899c

Tx prefix hash: 2c13f6b7001195f3553ae853720a977f470cb10ac5a23ed2c4e020ed54acd2ce
Tx public key: 133522892934a96d6ce60e0d0041ebce5acfa915b7e2ab6b848b98473bf9404b
Timestamp: 1634297416 Timestamp [UCT]: 2021-10-15 11:30:16 Age [y:d:h:m:s]: 03:147:12:39:46
Block: 353548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 883055 RingCT/type: yes/0
Extra: 01133522892934a96d6ce60e0d0041ebce5acfa915b7e2ab6b848b98473bf9404b02110000000c5410958b000000000000000000

1 output(s) for total of 41.357009689000 dcy

stealth address amount amount idx
00: ea8a7dca0519932b4f3a9747360aeaef82a3a106c5827be9336efc94d9223c8b 41.357009689000 722426 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": 353558, "vin": [ { "gen": { "height": 353548 } } ], "vout": [ { "amount": 41357009689, "target": { "key": "ea8a7dca0519932b4f3a9747360aeaef82a3a106c5827be9336efc94d9223c8b" } } ], "extra": [ 1, 19, 53, 34, 137, 41, 52, 169, 109, 108, 230, 14, 13, 0, 65, 235, 206, 90, 207, 169, 21, 183, 226, 171, 107, 132, 139, 152, 71, 59, 249, 64, 75, 2, 17, 0, 0, 0, 12, 84, 16, 149, 139, 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