Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecdd76b42389bac8e137afaa86e3588e71ddea3154cb6ba9cb65430f9d035557

Tx prefix hash: ecde7216f0edcdaf2e580cb45a45d6110bb38c7dd68a526f64f412b8c7454296
Tx public key: 17f5ecd3305dd46c5a117ba8aa9b5c92bdc58548a3f136b3359ab5477b1b30a2
Timestamp: 1675384237 Timestamp [UCT]: 2023-02-03 00:30:37 Age [y:d:h:m:s]: 01:303:20:14:08
Block: 688547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478123 RingCT/type: yes/0
Extra: 0117f5ecd3305dd46c5a117ba8aa9b5c92bdc58548a3f136b3359ab5477b1b30a20211000000037e406890000000000000000000

1 output(s) for total of 3.210390707000 dcy

stealth address amount amount idx
00: 6fbd582b3d05a66ffb41bc91a753b89393a8e4e44837a17870c07354be790741 3.210390707000 1131171 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": 688557, "vin": [ { "gen": { "height": 688547 } } ], "vout": [ { "amount": 3210390707, "target": { "key": "6fbd582b3d05a66ffb41bc91a753b89393a8e4e44837a17870c07354be790741" } } ], "extra": [ 1, 23, 245, 236, 211, 48, 93, 212, 108, 90, 17, 123, 168, 170, 155, 92, 146, 189, 197, 133, 72, 163, 241, 54, 179, 53, 154, 181, 71, 123, 27, 48, 162, 2, 17, 0, 0, 0, 3, 126, 64, 104, 144, 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