Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 899d01ef0eca9bd3b11c340d809467766be117d41fb68b4a56bedc1910dd6f27

Tx prefix hash: 82cd53d6378be7f0a58d291ae350af38c44177f1b26d6432a6af4904f4b6c7c0
Tx public key: 716362aeb79f51ea5d272e44cddb7d3a2fd70595a69a2cca0882f4663ed83ddb
Timestamp: 1737377167 Timestamp [UCT]: 2025-01-20 12:46:07 Age [y:d:h:m:s]: 00:148:23:45:47
Block: 1201422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106235 RingCT/type: yes/0
Extra: 01716362aeb79f51ea5d272e44cddb7d3a2fd70595a69a2cca0882f4663ed83ddb021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74a9f9570ccec9f5b0344fad36c48d3ecbbf7b89f4a09cfdbc3605edd322f75e 0.600000000000 1688075 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": 1201432, "vin": [ { "gen": { "height": 1201422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74a9f9570ccec9f5b0344fad36c48d3ecbbf7b89f4a09cfdbc3605edd322f75e" } } ], "extra": [ 1, 113, 99, 98, 174, 183, 159, 81, 234, 93, 39, 46, 68, 205, 219, 125, 58, 47, 215, 5, 149, 166, 154, 44, 202, 8, 130, 244, 102, 62, 216, 61, 219, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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