Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8dbb2d4af703c5386bd8fe029c941795d873b91e695f121b6e965409e1edc90

Tx prefix hash: 0af14ac8e89e537106f791bcc9488026a3fb355a5c0c8420fb08b21beea9375b
Tx public key: c2f2ca9eeac97835b8a65fa669f9509ff6db3db8d089a92370fcbfc68c3acb2d
Timestamp: 1713793427 Timestamp [UCT]: 2024-04-22 13:43:47 Age [y:d:h:m:s]: 01:023:10:56:05
Block: 1006105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277708 RingCT/type: yes/0
Extra: 01c2f2ca9eeac97835b8a65fa669f9509ff6db3db8d089a92370fcbfc68c3acb2d02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12daaabc937c989ccf158d472a8cdca34bbdd69bc877a5c78a24c6bd49d6a6b5 0.600000000000 1467023 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": 1006115, "vin": [ { "gen": { "height": 1006105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12daaabc937c989ccf158d472a8cdca34bbdd69bc877a5c78a24c6bd49d6a6b5" } } ], "extra": [ 1, 194, 242, 202, 158, 234, 201, 120, 53, 184, 166, 95, 166, 105, 249, 80, 159, 246, 219, 61, 184, 208, 137, 169, 35, 112, 252, 191, 198, 140, 58, 203, 45, 2, 17, 0, 0, 0, 4, 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