Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54d30a7ff2dcccf5f76b779df1e052b3dfec53a33f921ce5627a5206761e3b98

Tx prefix hash: 475f3961fbf8c6e818c3105669f07f2aab8247d0e71461088161caa3a15d7fec
Tx public key: 56736e3aa02a4de5cdca5b40d745f638f479037f60fe2551de2d84c8b811ef02
Timestamp: 1704123369 Timestamp [UCT]: 2024-01-01 15:36:09 Age [y:d:h:m:s]: 01:079:14:29:52
Block: 925928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318005 RingCT/type: yes/0
Extra: 0156736e3aa02a4de5cdca5b40d745f638f479037f60fe2551de2d84c8b811ef020211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 389262608b92cd92027b5f42f0d8b0ceaff4b8043a0144ceb78e1a82b0071468 0.600000000000 1383698 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": 925938, "vin": [ { "gen": { "height": 925928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "389262608b92cd92027b5f42f0d8b0ceaff4b8043a0144ceb78e1a82b0071468" } } ], "extra": [ 1, 86, 115, 110, 58, 160, 42, 77, 229, 205, 202, 91, 64, 215, 69, 246, 56, 244, 121, 3, 127, 96, 254, 37, 81, 222, 45, 132, 200, 184, 17, 239, 2, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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