Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9394f91365f2a9879fb559ad208c312d2ff69bdbe96e4baa5e3dcd4f5eb2a98

Tx prefix hash: 44928c7bc0ae06e8e5dc898becf7df37acaa6d716f780b15d7e90c35c3a3a79b
Tx public key: 66416389bf90640f63c7d64f31803ced815a779067e57b22d4b3e88825ae1960
Timestamp: 1684664859 Timestamp [UCT]: 2023-05-21 10:27:39 Age [y:d:h:m:s]: 02:029:10:47:19
Block: 764864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 543033 RingCT/type: yes/0
Extra: 0166416389bf90640f63c7d64f31803ced815a779067e57b22d4b3e88825ae196002110000000275e3f0e9000000000000000000

1 output(s) for total of 1.793445729000 dcy

stealth address amount amount idx
00: 5e2f014a50c8a56fb0368e61c5c083ea0c1ea7fb1df706f5d1fb0de14e9acbf9 1.793445729000 1213817 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": 764874, "vin": [ { "gen": { "height": 764864 } } ], "vout": [ { "amount": 1793445729, "target": { "key": "5e2f014a50c8a56fb0368e61c5c083ea0c1ea7fb1df706f5d1fb0de14e9acbf9" } } ], "extra": [ 1, 102, 65, 99, 137, 191, 144, 100, 15, 99, 199, 214, 79, 49, 128, 60, 237, 129, 90, 119, 144, 103, 229, 123, 34, 212, 179, 232, 136, 37, 174, 25, 96, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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