Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e426c3d846fcb18d951b5a20662a56ca886d2e3ad8cd5388186fec7572b927b1

Tx prefix hash: fab0d82120f68e190cbddb76cd6d2d70fbad6da2bbc573b69c2c2ae69db79d7e
Tx public key: 701a07ff0026c8d06282ca2868f38812e9d8fdf6590f594639d45dca593c973e
Timestamp: 1735452316 Timestamp [UCT]: 2024-12-29 06:05:16 Age [y:d:h:m:s]: 00:096:10:17:56
Block: 1185527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68714 RingCT/type: yes/0
Extra: 01701a07ff0026c8d06282ca2868f38812e9d8fdf6590f594639d45dca593c973e0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 398ed9fc3ace8f80290e6aeb3b0d26d1fdbef237cf25325aa9f3d5af439a0695 0.600000000000 1672000 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": 1185537, "vin": [ { "gen": { "height": 1185527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "398ed9fc3ace8f80290e6aeb3b0d26d1fdbef237cf25325aa9f3d5af439a0695" } } ], "extra": [ 1, 112, 26, 7, 255, 0, 38, 200, 208, 98, 130, 202, 40, 104, 243, 136, 18, 233, 216, 253, 246, 89, 15, 89, 70, 57, 212, 93, 202, 89, 60, 151, 62, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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