Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3356715b574d9dde47352741d81a9613494e4d3e245a9ad3ebd72e26b622f0f3

Tx prefix hash: f093537d01057f4e3586016198b0b1efd50240503b8056550b68b52e94f728dc
Tx public key: 3ef3d9ed1cdc4cc6bd9e6ee17c2abf73ba7c0a825e2db3ba67fd8fccea7d79ff
Timestamp: 1582128377 Timestamp [UCT]: 2020-02-19 16:06:17 Age [y:d:h:m:s]: 05:259:17:47:26
Block: 68263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1336444 RingCT/type: yes/0
Extra: 013ef3d9ed1cdc4cc6bd9e6ee17c2abf73ba7c0a825e2db3ba67fd8fccea7d79ff0211000000044ac5aa02000000000000000000

1 output(s) for total of 364.600407661000 dcy

stealth address amount amount idx
00: 924cce9a373a6e83bb931a95adba368d555acb0ae38d7533156f3fa416dd3d07 364.600407661000 125793 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": 68273, "vin": [ { "gen": { "height": 68263 } } ], "vout": [ { "amount": 364600407661, "target": { "key": "924cce9a373a6e83bb931a95adba368d555acb0ae38d7533156f3fa416dd3d07" } } ], "extra": [ 1, 62, 243, 217, 237, 28, 220, 76, 198, 189, 158, 110, 225, 124, 42, 191, 115, 186, 124, 10, 130, 94, 45, 179, 186, 103, 253, 143, 204, 234, 125, 121, 255, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 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