Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d63fddb3f005d8371e4113ce991e38aa18ad9ab6c21b7948e95b2e233aee4359

Tx prefix hash: f1e9f8ac8606d7e7839e5a13300a2a27373dab0190aa886b2200eab6bcfc6f9b
Tx public key: 19c1d69fb923e85c86dd9f895d95f5f7466f1589a0ceb59ae7856943d9f3ec20
Timestamp: 1582507855 Timestamp [UCT]: 2020-02-24 01:30:55 Age [y:d:h:m:s]: 04:277:07:23:23
Block: 71072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1090939 RingCT/type: yes/0
Extra: 0119c1d69fb923e85c86dd9f895d95f5f7466f1589a0ceb59ae7856943d9f3ec2002110000000212c4732d000000000000000000

1 output(s) for total of 356.869771444000 dcy

stealth address amount amount idx
00: f59e489f20ce016440db2b0cecc124f2ea9286ca04c51927dcc1f935b62abd4f 356.869771444000 131370 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": 71082, "vin": [ { "gen": { "height": 71072 } } ], "vout": [ { "amount": 356869771444, "target": { "key": "f59e489f20ce016440db2b0cecc124f2ea9286ca04c51927dcc1f935b62abd4f" } } ], "extra": [ 1, 25, 193, 214, 159, 185, 35, 232, 92, 134, 221, 159, 137, 93, 149, 245, 247, 70, 111, 21, 137, 160, 206, 181, 154, 231, 133, 105, 67, 217, 243, 236, 32, 2, 17, 0, 0, 0, 2, 18, 196, 115, 45, 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