Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98efbec657f0a90911b484f3368da10aebe556e43b7006bd4116be9f021921de

Tx prefix hash: abc7ff35b8a4f38763836e84fb9c12d4fe85c41b0784fc90c763a4a4e90ba848
Tx public key: 12b58031c5ba630007e740dd95b923c44b64b962ba74f3b4e856b7a02effdd2c
Timestamp: 1727304480 Timestamp [UCT]: 2024-09-25 22:48:00 Age [y:d:h:m:s]: 01:046:06:39:04
Block: 1118115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291463 RingCT/type: yes/0
Extra: 0112b58031c5ba630007e740dd95b923c44b64b962ba74f3b4e856b7a02effdd2c021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 448bd3f8b9e5fbde79f12987e8c563d5afca2e6e3ef99cf33fed444361420fd4 0.600000000000 1599194 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": 1118125, "vin": [ { "gen": { "height": 1118115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "448bd3f8b9e5fbde79f12987e8c563d5afca2e6e3ef99cf33fed444361420fd4" } } ], "extra": [ 1, 18, 181, 128, 49, 197, 186, 99, 0, 7, 231, 64, 221, 149, 185, 35, 196, 75, 100, 185, 98, 186, 116, 243, 180, 232, 86, 183, 160, 46, 255, 221, 44, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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