Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad00e06b9eb4bc3319719ab089b7cd7c07da4e620dd14ce2d1388453b6a55d37

Tx prefix hash: cbb447e5cab74f26d63d7a2ec33c2d9733d7d7ef41876b58ee6a2afac7b7c6b0
Tx public key: e2207adea7fef35273dcc033455d388d53b513dccde6d7a47d8eeb9d0993e353
Timestamp: 1681708158 Timestamp [UCT]: 2023-04-17 05:09:18 Age [y:d:h:m:s]: 01:270:16:41:19
Block: 740338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454962 RingCT/type: yes/0
Extra: 01e2207adea7fef35273dcc033455d388d53b513dccde6d7a47d8eeb9d0993e353021100000001e6d27f9c000000000000000000

1 output(s) for total of 2.162484954000 dcy

stealth address amount amount idx
00: f38f0a0cf06a21a8988214f4db541ddc32a7d1e0822d694ef63d67a3c4007f7a 2.162484954000 1187231 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": 740348, "vin": [ { "gen": { "height": 740338 } } ], "vout": [ { "amount": 2162484954, "target": { "key": "f38f0a0cf06a21a8988214f4db541ddc32a7d1e0822d694ef63d67a3c4007f7a" } } ], "extra": [ 1, 226, 32, 122, 222, 167, 254, 243, 82, 115, 220, 192, 51, 69, 93, 56, 141, 83, 181, 19, 220, 205, 230, 215, 164, 125, 142, 235, 157, 9, 147, 227, 83, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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