Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42656dff70fa25373c5c409ae5c1287e849213f1e382ef502f54e5c859353c7f

Tx prefix hash: 44e89b50973e29eddf6af9c402a4eefc17c999add8c96c70068b5b60453d6e17
Tx public key: c45b174805eb470e161dcc466c17c89c2a58943efe19313f8aca180ff13a8e0a
Timestamp: 1724086244 Timestamp [UCT]: 2024-08-19 16:50:44 Age [y:d:h:m:s]: 00:232:03:23:01
Block: 1091433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165773 RingCT/type: yes/0
Extra: 01c45b174805eb470e161dcc466c17c89c2a58943efe19313f8aca180ff13a8e0a02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1c31a518b637f06ce0bde974a352e585cf4f6f9c1a8f553b097cccae95109f3 0.600000000000 1566064 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": 1091443, "vin": [ { "gen": { "height": 1091433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1c31a518b637f06ce0bde974a352e585cf4f6f9c1a8f553b097cccae95109f3" } } ], "extra": [ 1, 196, 91, 23, 72, 5, 235, 71, 14, 22, 29, 204, 70, 108, 23, 200, 156, 42, 88, 148, 62, 254, 25, 49, 63, 138, 202, 24, 15, 241, 58, 142, 10, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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