Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d775ed0763ff442b2bbc06a70cbfbf54e18d92a27feb90af376f2fa6076e1b8f

Tx prefix hash: ea47074f2d196bf80f881f588cf7fa2ed8a0666dc47afd45c35c0dc0f68cdd67
Tx public key: f7c63116605c0e9d603e9b80bc07349b2e6b3e6135bd0883fa3423b0631dfa6e
Timestamp: 1737419815 Timestamp [UCT]: 2025-01-21 00:36:55 Age [y:d:h:m:s]: 00:149:04:50:18
Block: 1201785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106349 RingCT/type: yes/0
Extra: 01f7c63116605c0e9d603e9b80bc07349b2e6b3e6135bd0883fa3423b0631dfa6e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d282e91cdc470e799844859571cedd4e00e48737fc7bfc7df6696e65e2f15b21 0.600000000000 1688442 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": 1201795, "vin": [ { "gen": { "height": 1201785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d282e91cdc470e799844859571cedd4e00e48737fc7bfc7df6696e65e2f15b21" } } ], "extra": [ 1, 247, 198, 49, 22, 96, 92, 14, 157, 96, 62, 155, 128, 188, 7, 52, 155, 46, 107, 62, 97, 53, 189, 8, 131, 250, 52, 35, 176, 99, 29, 250, 110, 2, 17, 0, 0, 0, 3, 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