Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 768f8e528ba30ef11952f031c63e9177fed6f755c919d07bc756e26e9f3eb941

Tx prefix hash: ca7bd27465eed210d628285b6763157e57b5cf55437b615b2bd77dd0284021c8
Tx public key: 659d5b92d826b4fdc7f966d506be6e6ee37acb18c770dfe665d154a4f2e465ed
Timestamp: 1711541047 Timestamp [UCT]: 2024-03-27 12:04:07 Age [y:d:h:m:s]: 01:079:20:02:33
Block: 987455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317956 RingCT/type: yes/0
Extra: 01659d5b92d826b4fdc7f966d506be6e6ee37acb18c770dfe665d154a4f2e465ed02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 614ea9070b69b9ebb3e3907f0a615bdb7f208f33ee99db899409efda4927f4c2 0.600010000000 1447704 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": 987465, "vin": [ { "gen": { "height": 987455 } } ], "vout": [ { "amount": 600010000, "target": { "key": "614ea9070b69b9ebb3e3907f0a615bdb7f208f33ee99db899409efda4927f4c2" } } ], "extra": [ 1, 101, 157, 91, 146, 216, 38, 180, 253, 199, 249, 102, 213, 6, 190, 110, 110, 227, 122, 203, 24, 199, 112, 223, 230, 101, 209, 84, 164, 242, 228, 101, 237, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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