Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31ef87b979706ea26673b61caf3a551a70f18dbb4f78ce7933c671f31aa1cec6

Tx prefix hash: 2c004adc1c91b0545a7e2fdd4f3fb6a84dc821b14c9ff1232cef9e014b4c5fa8
Tx public key: 37776449e93b2e20fb83fdc08a271a617dcc673bf978c1f6cdc4de5f66a7fc4e
Timestamp: 1708211044 Timestamp [UCT]: 2024-02-17 23:04:04 Age [y:d:h:m:s]: 01:119:02:27:48
Block: 959817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346100 RingCT/type: yes/0
Extra: 0137776449e93b2e20fb83fdc08a271a617dcc673bf978c1f6cdc4de5f66a7fc4e02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f0de6ff98c7966bfe9d7473f0f2a8bd70ada47233a4dc4435f461a09868d322 0.600000000000 1419376 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": 959827, "vin": [ { "gen": { "height": 959817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f0de6ff98c7966bfe9d7473f0f2a8bd70ada47233a4dc4435f461a09868d322" } } ], "extra": [ 1, 55, 119, 100, 73, 233, 59, 46, 32, 251, 131, 253, 192, 138, 39, 26, 97, 125, 204, 103, 59, 249, 120, 193, 246, 205, 196, 222, 95, 102, 167, 252, 78, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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