Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 511a6063895a0391d1c81066e978a8ebaba8f3d970ad9f8dadfd55cb8f0a5fe7

Tx prefix hash: c34deafd9ece63025fc83d198822fd62e3f54b70caa915f0ff6fbbabdc35a834
Tx public key: 054ae4325d0e685ebcdbeea8db110fb181ee0c6bdc1a33dd9fa903b2093e443d
Timestamp: 1740318800 Timestamp [UCT]: 2025-02-23 13:53:20 Age [y:d:h:m:s]: 00:227:13:43:56
Block: 1225536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160367 RingCT/type: yes/0
Extra: 01054ae4325d0e685ebcdbeea8db110fb181ee0c6bdc1a33dd9fa903b2093e443d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 167bde77f63689b20740a35334eb7ef46c44f9b7c414d299596ff8bda9238122 0.600000000000 1712401 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": 1225546, "vin": [ { "gen": { "height": 1225536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "167bde77f63689b20740a35334eb7ef46c44f9b7c414d299596ff8bda9238122" } } ], "extra": [ 1, 5, 74, 228, 50, 93, 14, 104, 94, 188, 219, 238, 168, 219, 17, 15, 177, 129, 238, 12, 107, 220, 26, 51, 221, 159, 169, 3, 178, 9, 62, 68, 61, 2, 17, 0, 0, 0, 3, 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