Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 631589d9f287034e3fedb7d195d93d781c7a517e213ec6a49ca622860f07a91d

Tx prefix hash: 82d8a22d42467e17cd50d581e706f34b44a7204faadfaed4126b62a8f82ca36d
Tx public key: ab8dcb5c5e45f6fcf6904076ce1459e2d04645e3e4b75b5a360c408751ff44a1
Timestamp: 1685092655 Timestamp [UCT]: 2023-05-26 09:17:35 Age [y:d:h:m:s]: 02:192:01:38:58
Block: 768406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 657102 RingCT/type: yes/0
Extra: 01ab8dcb5c5e45f6fcf6904076ce1459e2d04645e3e4b75b5a360c408751ff44a1021100000001b3164c24000000000000000000

1 output(s) for total of 1.745629681000 dcy

stealth address amount amount idx
00: 9d15916098b77e38b645c6130a608a30997898d972fa52282d25d100407084d0 1.745629681000 1217601 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": 768416, "vin": [ { "gen": { "height": 768406 } } ], "vout": [ { "amount": 1745629681, "target": { "key": "9d15916098b77e38b645c6130a608a30997898d972fa52282d25d100407084d0" } } ], "extra": [ 1, 171, 141, 203, 92, 94, 69, 246, 252, 246, 144, 64, 118, 206, 20, 89, 226, 208, 70, 69, 227, 228, 183, 91, 90, 54, 12, 64, 135, 81, 255, 68, 161, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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