Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a545f5462322c43954728ae7b08505276c94e3a53371f5baa3e590124471fe4

Tx prefix hash: b946193a1fc42d642cea49b671fc80deedb221ffba810a843563451c7b70c932
Tx public key: a6d1fedb2d80f718875cd8b8c4ccd3f04b9d25488ff9d446da9b71f17133a874
Timestamp: 1704298933 Timestamp [UCT]: 2024-01-03 16:22:13 Age [y:d:h:m:s]: 01:054:23:33:17
Block: 927396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300357 RingCT/type: yes/0
Extra: 01a6d1fedb2d80f718875cd8b8c4ccd3f04b9d25488ff9d446da9b71f17133a8740211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f5deee8227adb7ad7a0177c5b7c7b6aaf4f7c69f39a536cedb4be684c2a78f4 0.600000000000 1385232 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": 927406, "vin": [ { "gen": { "height": 927396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f5deee8227adb7ad7a0177c5b7c7b6aaf4f7c69f39a536cedb4be684c2a78f4" } } ], "extra": [ 1, 166, 209, 254, 219, 45, 128, 247, 24, 135, 92, 216, 184, 196, 204, 211, 240, 75, 157, 37, 72, 143, 249, 212, 70, 218, 155, 113, 241, 113, 51, 168, 116, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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