Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3f3ba94c053a5847c273257133ac43f6c8aa0c7382b70dddc713c4d45c319a5

Tx prefix hash: 7c51e4ca735cc907fc2c6dd45dfc2d60a16a4eee37258ce17ff7776216ccf032
Tx public key: a38d77ca07bc4a3c104b0203ce57bffdca4a270723e3eb371d091cfa6b6c0565
Timestamp: 1736529460 Timestamp [UCT]: 2025-01-10 17:17:40 Age [y:d:h:m:s]: 00:087:19:50:34
Block: 1194449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62546 RingCT/type: yes/0
Extra: 01a38d77ca07bc4a3c104b0203ce57bffdca4a270723e3eb371d091cfa6b6c05650211000000048368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d518e97f21e6f7a13988983292e6178d9d807bd1d7945f364bad85a356a90d58 0.600000000000 1681020 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": 1194459, "vin": [ { "gen": { "height": 1194449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d518e97f21e6f7a13988983292e6178d9d807bd1d7945f364bad85a356a90d58" } } ], "extra": [ 1, 163, 141, 119, 202, 7, 188, 74, 60, 16, 75, 2, 3, 206, 87, 191, 253, 202, 74, 39, 7, 35, 227, 235, 55, 29, 9, 28, 250, 107, 108, 5, 101, 2, 17, 0, 0, 0, 4, 131, 104, 38, 109, 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