Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 733cd4ce84c36692f918a6486871065bcb8b9ea9712285c7c9d4ee09deb6737d

Tx prefix hash: 6960f2169a0447ae131e993dbd07510c63691b6f138ec5ffcfb609e36aea20cb
Tx public key: 22421109cf6462f26c3060d6139f4b4f1d971baa40a350440cd48d0a75cf4425
Timestamp: 1702520819 Timestamp [UCT]: 2023-12-14 02:26:59 Age [y:d:h:m:s]: 01:165:19:34:20
Block: 912641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379684 RingCT/type: yes/0
Extra: 0122421109cf6462f26c3060d6139f4b4f1d971baa40a350440cd48d0a75cf4425021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a96ced692c1d2d7f0a8201e6432c58d4d0e98ea689644c456e66ac6a9c045f8d 0.600000000000 1369873 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": 912651, "vin": [ { "gen": { "height": 912641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a96ced692c1d2d7f0a8201e6432c58d4d0e98ea689644c456e66ac6a9c045f8d" } } ], "extra": [ 1, 34, 66, 17, 9, 207, 100, 98, 242, 108, 48, 96, 214, 19, 159, 75, 79, 29, 151, 27, 170, 64, 163, 80, 68, 12, 212, 141, 10, 117, 207, 68, 37, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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