Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98df3d087b022f694ae3b6aa0a4d738a19a6af28a26179981bb8393ff2881a0a

Tx prefix hash: 4b085a22a11eecc0e9ec58e6773d07caadca55eab61fada0d0a38e03dbaa62d0
Tx public key: 7e20994c7a36e16866933e89fa03e93a2d3160dc62d3593e3935eb000870c82d
Timestamp: 1673843286 Timestamp [UCT]: 2023-01-16 04:28:06 Age [y:d:h:m:s]: 02:081:07:24:30
Block: 675754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 579781 RingCT/type: yes/0
Extra: 017e20994c7a36e16866933e89fa03e93a2d3160dc62d3593e3935eb000870c82d021100000003faf35c9c000000000000000000

1 output(s) for total of 3.539536767000 dcy

stealth address amount amount idx
00: ebea4567b0f79d9eb859d4bd7e453bfb690ef29f53669281cada1fe88af3a4c5 3.539536767000 1117437 of 0

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": 675764, "vin": [ { "gen": { "height": 675754 } } ], "vout": [ { "amount": 3539536767, "target": { "key": "ebea4567b0f79d9eb859d4bd7e453bfb690ef29f53669281cada1fe88af3a4c5" } } ], "extra": [ 1, 126, 32, 153, 76, 122, 54, 225, 104, 102, 147, 62, 137, 250, 3, 233, 58, 45, 49, 96, 220, 98, 211, 89, 62, 57, 53, 235, 0, 8, 112, 200, 45, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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