Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 820f739fe15aa29c96a17e9e31f63004fe9f8742979ee9cc0010cd0f03f4b927

Tx prefix hash: 26cf6c422b509cb637fe124029bed8b0fede65115da3d55a14b704015912c09f
Tx public key: e413587396dfbc3fdc971ee5d6e2b6bc669c3579dedb0a75a61732669982dc9c
Timestamp: 1719912979 Timestamp [UCT]: 2024-07-02 09:36:19 Age [y:d:h:m:s]: 00:317:22:16:59
Block: 1056839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227183 RingCT/type: yes/0
Extra: 01e413587396dfbc3fdc971ee5d6e2b6bc669c3579dedb0a75a61732669982dc9c02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cb09acf5119190ed174e25ef538447899035fb0ebf1a2f5e20a4644771c5c9f 0.600000000000 1527268 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": 1056849, "vin": [ { "gen": { "height": 1056839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cb09acf5119190ed174e25ef538447899035fb0ebf1a2f5e20a4644771c5c9f" } } ], "extra": [ 1, 228, 19, 88, 115, 150, 223, 188, 63, 220, 151, 30, 229, 214, 226, 182, 188, 102, 156, 53, 121, 222, 219, 10, 117, 166, 23, 50, 102, 153, 130, 220, 156, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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