Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a643f1b51a122cd12f6debcd4cb43023176d79e9501843a0bf60d9aebbce8312

Tx prefix hash: e7371123befb88b048f3d9f6ad3f7204381c81eb1990417e54293b565014e5e3
Tx public key: 85c1b86e70ff70dc2619c4a731825dc6ae40b3a7705951474e1866c73e24a2d5
Timestamp: 1734599013 Timestamp [UCT]: 2024-12-19 09:03:33 Age [y:d:h:m:s]: 00:108:13:50:59
Block: 1178496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77350 RingCT/type: yes/0
Extra: 0185c1b86e70ff70dc2619c4a731825dc6ae40b3a7705951474e1866c73e24a2d5021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 146565d954c8ad68a609bd2f6e4fa93504b8adf7d570740a00eb8fc653da943d 0.600000000000 1664883 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": 1178506, "vin": [ { "gen": { "height": 1178496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "146565d954c8ad68a609bd2f6e4fa93504b8adf7d570740a00eb8fc653da943d" } } ], "extra": [ 1, 133, 193, 184, 110, 112, 255, 112, 220, 38, 25, 196, 167, 49, 130, 93, 198, 174, 64, 179, 167, 112, 89, 81, 71, 78, 24, 102, 199, 62, 36, 162, 213, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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