Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65eb51b1f8fe8f3398b33bb81532052cf191a7674743d9f382862478487061cd

Tx prefix hash: 208abbbcc365cece1045a316cfefbf3b227690f22328a7ab23d5b1c015a03d5a
Tx public key: 2164dd10cd32e4a1786f8bafc23ed9dd3157f8fc464de7aae3a0f03b27065d6f
Timestamp: 1700755158 Timestamp [UCT]: 2023-11-23 15:59:18 Age [y:d:h:m:s]: 01:176:18:47:18
Block: 898011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387532 RingCT/type: yes/0
Extra: 012164dd10cd32e4a1786f8bafc23ed9dd3157f8fc464de7aae3a0f03b27065d6f02110000000333af99f4000000000000000000

1 output(s) for total of 0.649406694000 dcy

stealth address amount amount idx
00: e73eb0df4bc72849509a8e7dd6ba174d36bfe8332a95a5f4b300095e6966c716 0.649406694000 1354414 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": 898021, "vin": [ { "gen": { "height": 898011 } } ], "vout": [ { "amount": 649406694, "target": { "key": "e73eb0df4bc72849509a8e7dd6ba174d36bfe8332a95a5f4b300095e6966c716" } } ], "extra": [ 1, 33, 100, 221, 16, 205, 50, 228, 161, 120, 111, 139, 175, 194, 62, 217, 221, 49, 87, 248, 252, 70, 77, 231, 170, 227, 160, 240, 59, 39, 6, 93, 111, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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