Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d0fcb2df9ce0e8e68fe58952750e8d172364c77398606011a4f494425566632

Tx prefix hash: 25e42a0c1505603331ca5cfd7e57594e2ecc9c77deb77d782424fd70be3676a9
Tx public key: 339e1c1aa0ddec7c89a4fee08a563cd006ed72e0c3331e3394c1dbb273571eef
Timestamp: 1727947421 Timestamp [UCT]: 2024-10-03 09:23:41 Age [y:d:h:m:s]: 00:197:04:05:08
Block: 1123443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140730 RingCT/type: yes/0
Extra: 01339e1c1aa0ddec7c89a4fee08a563cd006ed72e0c3331e3394c1dbb273571eef021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41d35e8a2d5829465dd6bad50cb380f7e5b95323b6287b8d8baa736078ccb890 0.600000000000 1605978 of 15

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": 1123453, "vin": [ { "gen": { "height": 1123443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41d35e8a2d5829465dd6bad50cb380f7e5b95323b6287b8d8baa736078ccb890" } } ], "extra": [ 1, 51, 158, 28, 26, 160, 221, 236, 124, 137, 164, 254, 224, 138, 86, 60, 208, 6, 237, 114, 224, 195, 51, 30, 51, 148, 193, 219, 178, 115, 87, 30, 239, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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