Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e3195bcf825585219c000579901010179e4df3d35318623eac18f9243470954

Tx prefix hash: 9202436e699482dd496131699e990c54e5a64fda31a4b14fe00f05326d7e23b0
Tx public key: 14c3d165c757d3d05d0b2b00c78d5e0ac1c34b6af08d4401faefcfa98ffd64b3
Timestamp: 1662976223 Timestamp [UCT]: 2022-09-12 09:50:23 Age [y:d:h:m:s]: 03:072:17:10:55
Block: 586235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 831869 RingCT/type: yes/0
Extra: 0114c3d165c757d3d05d0b2b00c78d5e0ac1c34b6af08d4401faefcfa98ffd64b30211000000066035bcb5000000000000000000

1 output(s) for total of 7.007452563000 dcy

stealth address amount amount idx
00: daeeb0a368e0fe5b6e9aad59ed5e9040c28a24ee31d96c17fb3b3362c3e2480b 7.007452563000 1020322 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": 586245, "vin": [ { "gen": { "height": 586235 } } ], "vout": [ { "amount": 7007452563, "target": { "key": "daeeb0a368e0fe5b6e9aad59ed5e9040c28a24ee31d96c17fb3b3362c3e2480b" } } ], "extra": [ 1, 20, 195, 209, 101, 199, 87, 211, 208, 93, 11, 43, 0, 199, 141, 94, 10, 193, 195, 75, 106, 240, 141, 68, 1, 250, 239, 207, 169, 143, 253, 100, 179, 2, 17, 0, 0, 0, 6, 96, 53, 188, 181, 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