Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9c09c340dc9a489411719c9d3389192e45fe14efd4766e82235d88430cf41e6

Tx prefix hash: fa2f41815e1c688890ccfed09ff0fd18ab6fedc01929a01b22681d0f57bea12d
Tx public key: a6c87bf3d1e01055a582db2d4cb96a6e17724cdf85d7b43cdc8bb989149479f4
Timestamp: 1702229732 Timestamp [UCT]: 2023-12-10 17:35:32 Age [y:d:h:m:s]: 01:115:08:01:29
Block: 910227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343566 RingCT/type: yes/0
Extra: 01a6c87bf3d1e01055a582db2d4cb96a6e17724cdf85d7b43cdc8bb989149479f4021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 366b29a3ece1cc4fb72c39cdeb5966d734d487aa9d716a863a0eb221aa43a598 0.600000000000 1367372 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": 910237, "vin": [ { "gen": { "height": 910227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "366b29a3ece1cc4fb72c39cdeb5966d734d487aa9d716a863a0eb221aa43a598" } } ], "extra": [ 1, 166, 200, 123, 243, 209, 224, 16, 85, 165, 130, 219, 45, 76, 185, 106, 110, 23, 114, 76, 223, 133, 215, 180, 60, 220, 139, 185, 137, 20, 148, 121, 244, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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