Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: defb177368141d78620752e089e88879f20d6aaa458b3748922d1485fd3f3c46

Tx prefix hash: 799dfd520dfd0524207fb75a2f6e338f4a1508d0addcaa2b198faeaed7a11b1f
Tx public key: dbd7c18018d9b4b63923f145a0b56532fef35aa4dc82a5f498a0221959a7b771
Timestamp: 1732168404 Timestamp [UCT]: 2024-11-21 05:53:24 Age [y:d:h:m:s]: 00:003:00:48:41
Block: 1158337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2172 RingCT/type: yes/0
Extra: 01dbd7c18018d9b4b63923f145a0b56532fef35aa4dc82a5f498a0221959a7b771021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26e05704a7623ae0eccc256d95c3921b0533142c63453c07c2dcf255160fafef 0.600000000000 1643966 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": 1158347, "vin": [ { "gen": { "height": 1158337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26e05704a7623ae0eccc256d95c3921b0533142c63453c07c2dcf255160fafef" } } ], "extra": [ 1, 219, 215, 193, 128, 24, 217, 180, 182, 57, 35, 241, 69, 160, 181, 101, 50, 254, 243, 90, 164, 220, 130, 165, 244, 152, 160, 34, 25, 89, 167, 183, 113, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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