Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e59d90cbeff78471e1a25a67432cef08408bcf1ef23a965a214986a1270c392

Tx prefix hash: db0328661adf07c6ae7901d7ba982a80e7cfb1b0d2b0f3ff5d4d89e312994343
Tx public key: d8da052d0ac8899b4a61f5a6d73b6b54f2a8ab5b537d7938d6477b2e1e1d11b9
Timestamp: 1737853437 Timestamp [UCT]: 2025-01-26 01:03:57 Age [y:d:h:m:s]: 00:144:16:52:16
Block: 1205367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103154 RingCT/type: yes/0
Extra: 01d8da052d0ac8899b4a61f5a6d73b6b54f2a8ab5b537d7938d6477b2e1e1d11b9021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 441ee69d797ae8f7a4ba48ec09b7f249c3705fa28498928811e07be312349239 0.600000000000 1692064 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": 1205377, "vin": [ { "gen": { "height": 1205367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "441ee69d797ae8f7a4ba48ec09b7f249c3705fa28498928811e07be312349239" } } ], "extra": [ 1, 216, 218, 5, 45, 10, 200, 137, 155, 74, 97, 245, 166, 215, 59, 107, 84, 242, 168, 171, 91, 83, 125, 121, 56, 214, 71, 123, 46, 30, 29, 17, 185, 2, 17, 0, 0, 0, 5, 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