Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcc6f4103737db0d7a1394e863798d361f3e98ab4f82dd5182762fa2fc51e2e4

Tx prefix hash: 50879c024f44a966c484d5a49e7d05a78b0d9a09fc94ad83b4da8771fb50375b
Tx public key: 1f0353dde8a1e60f35f59066314bb40f7100864b843cc8bf1bdde175192b583f
Timestamp: 1727080009 Timestamp [UCT]: 2024-09-23 08:26:49 Age [y:d:h:m:s]: 00:191:07:42:20
Block: 1116256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136549 RingCT/type: yes/0
Extra: 011f0353dde8a1e60f35f59066314bb40f7100864b843cc8bf1bdde175192b583f021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa713f2aef73160ba1baa37d5c1c7cd2e0f918b9f064e05fdb6c755fb2fe94c8 0.600000000000 1596675 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": 1116266, "vin": [ { "gen": { "height": 1116256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa713f2aef73160ba1baa37d5c1c7cd2e0f918b9f064e05fdb6c755fb2fe94c8" } } ], "extra": [ 1, 31, 3, 83, 221, 232, 161, 230, 15, 53, 245, 144, 102, 49, 75, 180, 15, 113, 0, 134, 75, 132, 60, 200, 191, 27, 221, 225, 117, 25, 43, 88, 63, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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