Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a66e5bed1a9aa7fae416de2ddd861477708987f11da9dd0b9665a8b2d636a4d2

Tx prefix hash: da7b6e63bfc231034c6214256204c33fcd7f81ec4efe70e917649d712f6ba3ed
Tx public key: 3a3bccd99e3136c029e5c1e8c007ec5b1ac2a878c734e01d9de2875474f886fe
Timestamp: 1707848146 Timestamp [UCT]: 2024-02-13 18:15:46 Age [y:d:h:m:s]: 01:050:01:25:31
Block: 956804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296810 RingCT/type: yes/0
Extra: 013a3bccd99e3136c029e5c1e8c007ec5b1ac2a878c734e01d9de2875474f886fe0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9eade42eb2110fcd0281130157ef3a9190a5e43125ac76bb783aa2a61a253218 0.600000000000 1416114 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": 956814, "vin": [ { "gen": { "height": 956804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9eade42eb2110fcd0281130157ef3a9190a5e43125ac76bb783aa2a61a253218" } } ], "extra": [ 1, 58, 59, 204, 217, 158, 49, 54, 192, 41, 229, 193, 232, 192, 7, 236, 91, 26, 194, 168, 120, 199, 52, 224, 29, 157, 226, 135, 84, 116, 248, 134, 254, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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