Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99e686ee306d0fc0131c5ef9d291f3210ac76272202653d293ce6a78b02734ea

Tx prefix hash: 557e727b085e939bca4f30060dc3fadbb9ee149c9ccc092f96e7a507ba12466d
Tx public key: e3aa2802aa935bd4c2e568b6fce2c51097214428ac8b2feeeeeeac0ba4396ad6
Timestamp: 1712617387 Timestamp [UCT]: 2024-04-08 23:03:07 Age [y:d:h:m:s]: 00:320:23:27:05
Block: 996322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229479 RingCT/type: yes/0
Extra: 01e3aa2802aa935bd4c2e568b6fce2c51097214428ac8b2feeeeeeac0ba4396ad602110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d08f35d15cfd1dc033045049ff6d2bf4f2251fdf24b55930d6cfe6b1b50c48a 0.600000000000 1456740 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": 996332, "vin": [ { "gen": { "height": 996322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d08f35d15cfd1dc033045049ff6d2bf4f2251fdf24b55930d6cfe6b1b50c48a" } } ], "extra": [ 1, 227, 170, 40, 2, 170, 147, 91, 212, 194, 229, 104, 182, 252, 226, 197, 16, 151, 33, 68, 40, 172, 139, 47, 238, 238, 238, 172, 11, 164, 57, 106, 214, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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