Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51958b5e11f566f4628ab25cee962fa06ba3e9779b1eb1638784c4e9fd492aea

Tx prefix hash: 4ab43f1a7946b7ef1c269d28d2de72bcfb38cfdd426e51e38f033127e1af843b
Tx public key: 85cc22de1f8a816ed3ea7a599872859f6ef524662f071283a096d4bb0708d68c
Timestamp: 1714486338 Timestamp [UCT]: 2024-04-30 14:12:18 Age [y:d:h:m:s]: 00:345:00:45:18
Block: 1011843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246647 RingCT/type: yes/0
Extra: 0185cc22de1f8a816ed3ea7a599872859f6ef524662f071283a096d4bb0708d68c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83cca7cb95c789da6227066ae4ac52fa9e569975b3770fea0473f9a9a7516d49 0.600000000000 1474185 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": 1011853, "vin": [ { "gen": { "height": 1011843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83cca7cb95c789da6227066ae4ac52fa9e569975b3770fea0473f9a9a7516d49" } } ], "extra": [ 1, 133, 204, 34, 222, 31, 138, 129, 110, 211, 234, 122, 89, 152, 114, 133, 159, 110, 245, 36, 102, 47, 7, 18, 131, 160, 150, 212, 187, 7, 8, 214, 140, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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