Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7dee96e2ca180b71051ddca60d09ac96eb430ec16ccf12b8c6272c1e766777e1

Tx prefix hash: 4a1d3a877b24fbb6a1451fa9bcf4840cc1fc6c24455c30d20ac42db3c5f087b1
Tx public key: 091d834d4998b05be3b92d0a845001b61c2b6b9ab518c4aa4849639c3d07e076
Timestamp: 1732167900 Timestamp [UCT]: 2024-11-21 05:45:00 Age [y:d:h:m:s]: 01:071:12:06:21
Block: 1158326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309444 RingCT/type: yes/0
Extra: 01091d834d4998b05be3b92d0a845001b61c2b6b9ab518c4aa4849639c3d07e0760211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d86bbf0e06051316c7b1c4b3a1a219af9acf631c133a9a7a7c8634880fbbb2fc 0.600000000000 1643955 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": 1158336, "vin": [ { "gen": { "height": 1158326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d86bbf0e06051316c7b1c4b3a1a219af9acf631c133a9a7a7c8634880fbbb2fc" } } ], "extra": [ 1, 9, 29, 131, 77, 73, 152, 176, 91, 227, 185, 45, 10, 132, 80, 1, 182, 28, 43, 107, 154, 181, 24, 196, 170, 72, 73, 99, 156, 61, 7, 224, 118, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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