Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56f20a8251173f80d3d421e09077011c36dcc8f9bd2ca3a5e6389116bb7989b0

Tx prefix hash: 1dcef583927718e170ab921c9e1b92997ed956e96aa602c8b0bdf6e8d36cc0e3
Tx public key: a59cf25f09a4bc72f941257726a0308ffcb2be04f28badea3a159d9add33d222
Timestamp: 1722322679 Timestamp [UCT]: 2024-07-30 06:57:59 Age [y:d:h:m:s]: 00:237:03:15:07
Block: 1076816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169370 RingCT/type: yes/0
Extra: 01a59cf25f09a4bc72f941257726a0308ffcb2be04f28badea3a159d9add33d22202110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfd4b3f23157efeda1ae483e2391bf4c0e13966e0d446b0e8cad6c561114aae4 0.600000000000 1549357 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": 1076826, "vin": [ { "gen": { "height": 1076816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfd4b3f23157efeda1ae483e2391bf4c0e13966e0d446b0e8cad6c561114aae4" } } ], "extra": [ 1, 165, 156, 242, 95, 9, 164, 188, 114, 249, 65, 37, 119, 38, 160, 48, 143, 252, 178, 190, 4, 242, 139, 173, 234, 58, 21, 157, 154, 221, 51, 210, 34, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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