Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ff876587686403c915fd9eba3e66420ffcec4f39509c57bfe5fbe4010fcb7e4

Tx prefix hash: a3cc42c7075a6e1f237691c6ea5e6ab51967d1fc6df947f7f0de2e7e8f2667c8
Tx public key: 7de899e55348fc8ea71a985dc5d17931bd3056fd2c6bccfdbaa745ce53d41832
Timestamp: 1703705684 Timestamp [UCT]: 2023-12-27 19:34:44 Age [y:d:h:m:s]: 01:111:10:39:56
Block: 922467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340769 RingCT/type: yes/0
Extra: 017de899e55348fc8ea71a985dc5d17931bd3056fd2c6bccfdbaa745ce53d4183202110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b8ccb464e0fef703efe539a1c6f816049403223a81fc174314aba45af8b2de9 0.600000000000 1380165 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": 922477, "vin": [ { "gen": { "height": 922467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b8ccb464e0fef703efe539a1c6f816049403223a81fc174314aba45af8b2de9" } } ], "extra": [ 1, 125, 232, 153, 229, 83, 72, 252, 142, 167, 26, 152, 93, 197, 209, 121, 49, 189, 48, 86, 253, 44, 107, 204, 253, 186, 167, 69, 206, 83, 212, 24, 50, 2, 17, 0, 0, 0, 10, 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