Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9986b9fe9dfdbe136f2f10dbddd89a077a477b480235b131cb5e04fd5758e38

Tx prefix hash: 2321d4613f3798e52af8e932c7593632c9ed0ab49893359894475a106373ce25
Tx public key: d25ea5de5e5201c6ab4511e7a0c4161c6c4e729fc6fb30cf1cf6c01b4cac5445
Timestamp: 1706378113 Timestamp [UCT]: 2024-01-27 17:55:13 Age [y:d:h:m:s]: 01:081:00:50:17
Block: 944601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318992 RingCT/type: yes/0
Extra: 01d25ea5de5e5201c6ab4511e7a0c4161c6c4e729fc6fb30cf1cf6c01b4cac54450211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: faad4aa5bd1a5f52f8de35025f06d7443c5c88cc47b9c8a1a944aaf85a5b57c3 0.600000000000 1402883 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": 944611, "vin": [ { "gen": { "height": 944601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "faad4aa5bd1a5f52f8de35025f06d7443c5c88cc47b9c8a1a944aaf85a5b57c3" } } ], "extra": [ 1, 210, 94, 165, 222, 94, 82, 1, 198, 171, 69, 17, 231, 160, 196, 22, 28, 108, 78, 114, 159, 198, 251, 48, 207, 28, 246, 192, 27, 76, 172, 84, 69, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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