Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e91d4dbec162a8e0bfd721321e20c74e11bdb1a8b72c5a79e8e08dbec8411ab

Tx prefix hash: 786cdb72dc5e24965a66e2485f8294804c8f84e25a837158e54c640aa495c13c
Tx public key: 9aaa6c1377f8e57fd0f993b12cf3f17572bd683db6ae5232574e43a082e7ab79
Timestamp: 1656939879 Timestamp [UCT]: 2022-07-04 13:04:39 Age [y:d:h:m:s]: 02:299:06:15:16
Block: 536481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 735020 RingCT/type: yes/0
Extra: 019aaa6c1377f8e57fd0f993b12cf3f17572bd683db6ae5232574e43a082e7ab7902110000000e2e6b1fd5000000000000000000

1 output(s) for total of 10.242734019000 dcy

stealth address amount amount idx
00: 7d1d05751b5c3d6e45a606bf17c07292eabcd01f3c64581164510c2d1c78753b 10.242734019000 966250 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": 536491, "vin": [ { "gen": { "height": 536481 } } ], "vout": [ { "amount": 10242734019, "target": { "key": "7d1d05751b5c3d6e45a606bf17c07292eabcd01f3c64581164510c2d1c78753b" } } ], "extra": [ 1, 154, 170, 108, 19, 119, 248, 229, 127, 208, 249, 147, 177, 44, 243, 241, 117, 114, 189, 104, 61, 182, 174, 82, 50, 87, 78, 67, 160, 130, 231, 171, 121, 2, 17, 0, 0, 0, 14, 46, 107, 31, 213, 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