Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cc538a45c3ec9dae7aab1e47441a0bb3ecd98d158c8b83cace179697fb3a34a

Tx prefix hash: 95e20de5805301c89aebf3701dbac9d003afdbce6a0b73763bd3694202bff086
Tx public key: 87d66a83e3dc38fcd576ae64a4d72f1b097d4cd827d2538e7af0f345dcc537c1
Timestamp: 1699668316 Timestamp [UCT]: 2023-11-11 02:05:16 Age [y:d:h:m:s]: 01:135:20:14:24
Block: 889006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358254 RingCT/type: yes/0
Extra: 0187d66a83e3dc38fcd576ae64a4d72f1b097d4cd827d2538e7af0f345dcc537c102110000000433af99f4000000000000000000

1 output(s) for total of 0.695591198000 dcy

stealth address amount amount idx
00: ca1d9ce668eb54eb8952ff8f4671030df17846331daf4dce222d6375226b1cf5 0.695591198000 1344977 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": 889016, "vin": [ { "gen": { "height": 889006 } } ], "vout": [ { "amount": 695591198, "target": { "key": "ca1d9ce668eb54eb8952ff8f4671030df17846331daf4dce222d6375226b1cf5" } } ], "extra": [ 1, 135, 214, 106, 131, 227, 220, 56, 252, 213, 118, 174, 100, 164, 215, 47, 27, 9, 125, 76, 216, 39, 210, 83, 142, 122, 240, 243, 69, 220, 197, 55, 193, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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