Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f54abca7a4ce3a42ded73c737c9d1d0f0136756098c37a1aec30836fab168987

Tx prefix hash: ed7edcc0c9907a285b65904808c97168bc3ebb4175ee4c8ffe603a2805c0a6e4
Tx public key: 653375d27b0e8f154aeca7cc4831e7a59ee0532e829578a4734d0e1545cdbca9
Timestamp: 1699847679 Timestamp [UCT]: 2023-11-13 03:54:39 Age [y:d:h:m:s]: 01:147:16:01:55
Block: 890491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366711 RingCT/type: yes/0
Extra: 01653375d27b0e8f154aeca7cc4831e7a59ee0532e829578a4734d0e1545cdbca902110000000575e3f0e9000000000000000000

1 output(s) for total of 0.687754838000 dcy

stealth address amount amount idx
00: 6acd2dd8d8ec423794aea63110ee9e6c9409f69d52a5a5e673049642efc85a46 0.687754838000 1346514 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": 890501, "vin": [ { "gen": { "height": 890491 } } ], "vout": [ { "amount": 687754838, "target": { "key": "6acd2dd8d8ec423794aea63110ee9e6c9409f69d52a5a5e673049642efc85a46" } } ], "extra": [ 1, 101, 51, 117, 210, 123, 14, 143, 21, 74, 236, 167, 204, 72, 49, 231, 165, 158, 224, 83, 46, 130, 149, 120, 164, 115, 77, 14, 21, 69, 205, 188, 169, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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