Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fa77e9013a2b806fcf1c09603c8790b53eab8d22f2f9a46c8140caf22c626a8

Tx prefix hash: f2560399e0029949dd1736b17c6b6fd90d2a8773369297073ad730e14c9ab903
Tx public key: 71c0d3411bccd3ea383ac10a0b353513b7fc44f633d51fc14c3dd9b01d3860a5
Timestamp: 1702209673 Timestamp [UCT]: 2023-12-10 12:01:13 Age [y:d:h:m:s]: 01:116:02:19:02
Block: 910070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344112 RingCT/type: yes/0
Extra: 0171c0d3411bccd3ea383ac10a0b353513b7fc44f633d51fc14c3dd9b01d3860a502110000000ce6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d8e3432eddd8edfec33d8a060e40c8b385b595804a89cdb5cc6dd5e22d1cafd 0.600000000000 1367213 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": 910080, "vin": [ { "gen": { "height": 910070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d8e3432eddd8edfec33d8a060e40c8b385b595804a89cdb5cc6dd5e22d1cafd" } } ], "extra": [ 1, 113, 192, 211, 65, 27, 204, 211, 234, 56, 58, 193, 10, 11, 53, 53, 19, 183, 252, 68, 246, 51, 213, 31, 193, 76, 61, 217, 176, 29, 56, 96, 165, 2, 17, 0, 0, 0, 12, 230, 210, 127, 156, 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