Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c4bdd12142a41659c6a510203b9eadf6cb3c286d3b34688c5af4391ab50b049

Tx prefix hash: a222b7118a7dee3bb42b00261d073c5618936759597de1a288d2047386904058
Tx public key: e7e38e10d9dd83c570017cbf15e3dc2208c41627bf970427ae5e3e0c79389299
Timestamp: 1722607558 Timestamp [UCT]: 2024-08-02 14:05:58 Age [y:d:h:m:s]: 00:205:12:02:25
Block: 1079178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146729 RingCT/type: yes/0
Extra: 01e7e38e10d9dd83c570017cbf15e3dc2208c41627bf970427ae5e3e0c7938929902110000001791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83e4286d41c96933d9f92c7e7b3b38db45071f13fd5f878623d29e8659045d12 0.600000000000 1552015 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": 1079188, "vin": [ { "gen": { "height": 1079178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83e4286d41c96933d9f92c7e7b3b38db45071f13fd5f878623d29e8659045d12" } } ], "extra": [ 1, 231, 227, 142, 16, 217, 221, 131, 197, 112, 1, 124, 191, 21, 227, 220, 34, 8, 196, 22, 39, 191, 151, 4, 39, 174, 94, 62, 12, 121, 56, 146, 153, 2, 17, 0, 0, 0, 23, 145, 225, 60, 4, 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