Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb49ae2f845267ec5984b2f393a0b0b3f7c8c72491e2723c65187bec9a507771

Tx prefix hash: d9151973a79a5638fdf9d983430fef3e49f14916edfb7bde97538a3339e3bce2
Tx public key: af9d01936f231a93ea6d4cefda2d4a41e951a9c05c096945b7374494a442dac2
Timestamp: 1736113455 Timestamp [UCT]: 2025-01-05 21:44:15 Age [y:d:h:m:s]: 00:084:04:44:35
Block: 1191019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59943 RingCT/type: yes/0
Extra: 01af9d01936f231a93ea6d4cefda2d4a41e951a9c05c096945b7374494a442dac202110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20f3352fa73cb656a3fde59cf29352137ce13f5e3adb0e68968bf05c0c4ca630 0.600000000000 1677542 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": 1191029, "vin": [ { "gen": { "height": 1191019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20f3352fa73cb656a3fde59cf29352137ce13f5e3adb0e68968bf05c0c4ca630" } } ], "extra": [ 1, 175, 157, 1, 147, 111, 35, 26, 147, 234, 109, 76, 239, 218, 45, 74, 65, 233, 81, 169, 192, 92, 9, 105, 69, 183, 55, 68, 148, 164, 66, 218, 194, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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