Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f76685d546511bca93b2a26bf995b0b2a13f2feaac546edc60d9545c39db3821

Tx prefix hash: e1d11408cc18feeea2c85e7efe8892f6deccc9e7ad76f686b070408ffc8925ec
Tx public key: 4ce044379a3158098030628bce4c0cc897505d1e5630a1e8d13daf100fbbea7c
Timestamp: 1659188309 Timestamp [UCT]: 2022-07-30 13:38:29 Age [y:d:h:m:s]: 02:106:09:07:37
Block: 554999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 597402 RingCT/type: yes/0
Extra: 014ce044379a3158098030628bce4c0cc897505d1e5630a1e8d13daf100fbbea7c021100000001eae24e24000000000000000000

1 output(s) for total of 8.893199746000 dcy

stealth address amount amount idx
00: 33e07bd6814d46b25b04087c05e5d2130e0dc008860a17ab9428d578e8f5a00c 8.893199746000 986875 of 0

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": 555009, "vin": [ { "gen": { "height": 554999 } } ], "vout": [ { "amount": 8893199746, "target": { "key": "33e07bd6814d46b25b04087c05e5d2130e0dc008860a17ab9428d578e8f5a00c" } } ], "extra": [ 1, 76, 224, 68, 55, 154, 49, 88, 9, 128, 48, 98, 139, 206, 76, 12, 200, 151, 80, 93, 30, 86, 48, 161, 232, 209, 61, 175, 16, 15, 187, 234, 124, 2, 17, 0, 0, 0, 1, 234, 226, 78, 36, 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