Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ac91cdcff1e1e90642e71ed4e5e349d723c15e33338ea3e76a97d292217d2ac

Tx prefix hash: 8db7dfa2c318b5ab12791e9b9941745be9ccdb532a4e0dc45e85b2f11c2d3aaf
Tx public key: 2847ffb839dcb7c015909f4252fd1f6f301cad322848392dcac9a06bcde5322e
Timestamp: 1719860519 Timestamp [UCT]: 2024-07-01 19:01:59 Age [y:d:h:m:s]: 01:168:21:39:56
Block: 1056394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379302 RingCT/type: yes/0
Extra: 012847ffb839dcb7c015909f4252fd1f6f301cad322848392dcac9a06bcde5322e0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b76f054f442647ef51dbe92e6ecd28a21204a575e425a4b18058fbf78be71890 0.600000000000 1526807 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": 1056404, "vin": [ { "gen": { "height": 1056394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b76f054f442647ef51dbe92e6ecd28a21204a575e425a4b18058fbf78be71890" } } ], "extra": [ 1, 40, 71, 255, 184, 57, 220, 183, 192, 21, 144, 159, 66, 82, 253, 31, 111, 48, 28, 173, 50, 40, 72, 57, 45, 202, 201, 160, 107, 205, 229, 50, 46, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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