Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f50570b0866ccfdbd3ce7f7a68abf24c25dc4d3f5ea87ec220c72d915b68e88b

Tx prefix hash: 7b8e5fce66c85192678d433fe6d2f2be7e00345ce74701a493639ac47235c343
Tx public key: 643041109dee7f338a12e27236dd43726820a3003d424ea26e2bd3df9958e723
Timestamp: 1735693886 Timestamp [UCT]: 2025-01-01 01:11:26 Age [y:d:h:m:s]: 00:108:02:24:47
Block: 1187530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77053 RingCT/type: yes/0
Extra: 01643041109dee7f338a12e27236dd43726820a3003d424ea26e2bd3df9958e72302110000000f007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c551c4605c905be70467764ae444baee114204a8d42f86f0fb3facf80a722e0 0.600000000000 1674021 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": 1187540, "vin": [ { "gen": { "height": 1187530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c551c4605c905be70467764ae444baee114204a8d42f86f0fb3facf80a722e0" } } ], "extra": [ 1, 100, 48, 65, 16, 157, 238, 127, 51, 138, 18, 226, 114, 54, 221, 67, 114, 104, 32, 163, 0, 61, 66, 78, 162, 110, 43, 211, 223, 153, 88, 231, 35, 2, 17, 0, 0, 0, 15, 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