Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19881025b3e0d3b2c6138758d90043dc261338707118e7a425a5a44443f89dd9

Tx prefix hash: fdcbecef056fda1a597120f8fb864d9a7423fdaba4e46d0888445ef80ecb7654
Tx public key: 197070d07d2a0b2735c5aa7928fa605b9ec1af6ad411e4c660fd6bca6b3be3a1
Timestamp: 1723942119 Timestamp [UCT]: 2024-08-18 00:48:39 Age [y:d:h:m:s]: 00:228:12:46:50
Block: 1090245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163197 RingCT/type: yes/0
Extra: 01197070d07d2a0b2735c5aa7928fa605b9ec1af6ad411e4c660fd6bca6b3be3a102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b94f8bf02505ec1b46a4cdcf643554800fb3b1017a4af228ca1a197908170d3 0.600000000000 1564868 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": 1090255, "vin": [ { "gen": { "height": 1090245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b94f8bf02505ec1b46a4cdcf643554800fb3b1017a4af228ca1a197908170d3" } } ], "extra": [ 1, 25, 112, 112, 208, 125, 42, 11, 39, 53, 197, 170, 121, 40, 250, 96, 91, 158, 193, 175, 106, 212, 17, 228, 198, 96, 253, 107, 202, 107, 59, 227, 161, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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