Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c2d3c4e20c17829bb4286a6064e7ed6f17fb274fc4d522fa853d6acc0512a44

Tx prefix hash: 5fcb8d660fc297a8bbb27d4401a1d9c97661218fdda456cdfb85e828adfe7000
Tx public key: 9f6c11a1a6c76d73657a9ebd0370282fab14050dc453177710d7d107af3db97f
Timestamp: 1724415397 Timestamp [UCT]: 2024-08-23 12:16:37 Age [y:d:h:m:s]: 00:228:23:26:58
Block: 1094181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163502 RingCT/type: yes/0
Extra: 019f6c11a1a6c76d73657a9ebd0370282fab14050dc453177710d7d107af3db97f021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3f93e3830d205fc0611f29dbbe36eaa32fe8b73719d51fb7632212c4c8c4bef 0.600000000000 1569272 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": 1094191, "vin": [ { "gen": { "height": 1094181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3f93e3830d205fc0611f29dbbe36eaa32fe8b73719d51fb7632212c4c8c4bef" } } ], "extra": [ 1, 159, 108, 17, 161, 166, 199, 109, 115, 101, 122, 158, 189, 3, 112, 40, 47, 171, 20, 5, 13, 196, 83, 23, 119, 16, 215, 209, 7, 175, 61, 185, 127, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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