Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d1a9e761ead07904a5d9ec84dbb4e9503f93445f0003db88a376fefc0dc0b65

Tx prefix hash: 9896d0dbe19f3f892f73715cc14acf84bc0fd4a207b536194632946c68439739
Tx public key: 8cb24910ec60f63deda5fa85a7e39119be3274d66c72a9a5a3c5201e100845e9
Timestamp: 1741265286 Timestamp [UCT]: 2025-03-06 12:48:06 Age [y:d:h:m:s]: 00:006:04:45:29
Block: 1233398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4439 RingCT/type: yes/0
Extra: 018cb24910ec60f63deda5fa85a7e39119be3274d66c72a9a5a3c5201e100845e9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4269d80ed59a1a53ecf3eff0eb2004cde1a660d6db8d35aa6df30107c73668c7 0.600000000000 1720319 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": 1233408, "vin": [ { "gen": { "height": 1233398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4269d80ed59a1a53ecf3eff0eb2004cde1a660d6db8d35aa6df30107c73668c7" } } ], "extra": [ 1, 140, 178, 73, 16, 236, 96, 246, 61, 237, 165, 250, 133, 167, 227, 145, 25, 190, 50, 116, 214, 108, 114, 169, 165, 163, 197, 32, 30, 16, 8, 69, 233, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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