Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91e4c732852d5355f48fbb879675773b99363b4c4ba0d514b9934e78b5a8b6d8

Tx prefix hash: 6806136459f790fc202b29624a2726baecaf7c697713032d863b7a5a081d7356
Tx public key: a7278489819f33f8bf9c830bccc890f6f3e26ae452895e0bafcf4848b341e0a5
Timestamp: 1716429999 Timestamp [UCT]: 2024-05-23 02:06:39 Age [y:d:h:m:s]: 00:357:14:35:35
Block: 1027959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255614 RingCT/type: yes/0
Extra: 01a7278489819f33f8bf9c830bccc890f6f3e26ae452895e0bafcf4848b341e0a502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f7ccf7adde2189e9e90ea9ba03ea872a0f3238fbd78de28ac19c9fe9d85a0f7 0.600000000000 1495842 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": 1027969, "vin": [ { "gen": { "height": 1027959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f7ccf7adde2189e9e90ea9ba03ea872a0f3238fbd78de28ac19c9fe9d85a0f7" } } ], "extra": [ 1, 167, 39, 132, 137, 129, 159, 51, 248, 191, 156, 131, 11, 204, 200, 144, 246, 243, 226, 106, 228, 82, 137, 94, 11, 175, 207, 72, 72, 179, 65, 224, 165, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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