Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc2c8494f3ab4e1206ae44f486f54db5ad92f30f4139c6748bb8d2ac977b546f

Tx prefix hash: 1cd61d6a3b7e24d87a084a2bfc6ecb1cfb439d9b835bf2b3e48c91445f5e0340
Tx public key: e9b09d1b47ca295dc463739286d0d96c915ba72ea02e8f36a1daae764360133d
Timestamp: 1738222756 Timestamp [UCT]: 2025-01-30 07:39:16 Age [y:d:h:m:s]: 00:138:04:47:41
Block: 1208211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98743 RingCT/type: yes/0
Extra: 01e9b09d1b47ca295dc463739286d0d96c915ba72ea02e8f36a1daae764360133d021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 671b41bf9c79b59d422106c6c6aee553706b6ef52e3c94194bc92e7f4f8281ad 0.600000000000 1694940 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": 1208221, "vin": [ { "gen": { "height": 1208211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "671b41bf9c79b59d422106c6c6aee553706b6ef52e3c94194bc92e7f4f8281ad" } } ], "extra": [ 1, 233, 176, 157, 27, 71, 202, 41, 93, 196, 99, 115, 146, 134, 208, 217, 108, 145, 91, 167, 46, 160, 46, 143, 54, 161, 218, 174, 118, 67, 96, 19, 61, 2, 17, 0, 0, 0, 7, 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