Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34013b6e0fe7db8278a13fed52b22cfbf3d453194f2f65b3c6ef09b9b75e8e6b

Tx prefix hash: 5d2a69866faa6687def67e441b43aadf1b67e59c16b6a6091b2122d25d8ed6f6
Tx public key: 3972521a2bcc293035904825ae22f83c88d5ebcf0d91c1c12fe3230cf3bd147e
Timestamp: 1735212160 Timestamp [UCT]: 2024-12-26 11:22:40 Age [y:d:h:m:s]: 00:092:12:37:05
Block: 1183558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65900 RingCT/type: yes/0
Extra: 013972521a2bcc293035904825ae22f83c88d5ebcf0d91c1c12fe3230cf3bd147e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b318912591f95215cccae5437b9ba79c1d519e1ba6971b7d4b811dbe4d95b781 0.600000000000 1670003 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": 1183568, "vin": [ { "gen": { "height": 1183558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b318912591f95215cccae5437b9ba79c1d519e1ba6971b7d4b811dbe4d95b781" } } ], "extra": [ 1, 57, 114, 82, 26, 43, 204, 41, 48, 53, 144, 72, 37, 174, 34, 248, 60, 136, 213, 235, 207, 13, 145, 193, 193, 47, 227, 35, 12, 243, 189, 20, 126, 2, 17, 0, 0, 0, 2, 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