Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a3a72a8ebede681a09e51de1045982c7ce15d97fdad6583641afdb77884bc7a

Tx prefix hash: 5c9c6017778f3cbe1e88d9df9c5c4311541009ad0b67b6977e86e3cc41424053
Tx public key: d90efde982b0c877b803b58a2bc311424615a7658a6a0c93f9270961a626c681
Timestamp: 1713449530 Timestamp [UCT]: 2024-04-18 14:12:10 Age [y:d:h:m:s]: 00:224:05:12:44
Block: 1003236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160522 RingCT/type: yes/0
Extra: 01d90efde982b0c877b803b58a2bc311424615a7658a6a0c93f9270961a626c68102110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eacb328321a689e404ebe5c3851a4430ac2d35023af6b06a2ea91f4d7f7de5b3 0.600000000000 1463766 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": 1003246, "vin": [ { "gen": { "height": 1003236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eacb328321a689e404ebe5c3851a4430ac2d35023af6b06a2ea91f4d7f7de5b3" } } ], "extra": [ 1, 217, 14, 253, 233, 130, 176, 200, 119, 184, 3, 181, 138, 43, 195, 17, 66, 70, 21, 167, 101, 138, 106, 12, 147, 249, 39, 9, 97, 166, 38, 198, 129, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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