Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69f2421fff4752e268a03a249c10694f6f08ece7f87b6b5da00fe06fe3809bd3

Tx prefix hash: c811372d99fe91ab96e7d47bd9cdd2d1900ab37211a64f9db319206db074c0e4
Tx public key: 26ec7d84cfdd81fdc9f9530367301ea73c710a029a7769fa1e229ac8b8748372
Timestamp: 1725581685 Timestamp [UCT]: 2024-09-06 00:14:45 Age [y:d:h:m:s]: 01:087:11:59:24
Block: 1103836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320993 RingCT/type: yes/0
Extra: 0126ec7d84cfdd81fdc9f9530367301ea73c710a029a7769fa1e229ac8b8748372021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f5aa7ae0b1f0c753a5a6765cf64cf8fd4589e44bce013490deae0d842f8e4da 0.600000000000 1580817 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": 1103846, "vin": [ { "gen": { "height": 1103836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f5aa7ae0b1f0c753a5a6765cf64cf8fd4589e44bce013490deae0d842f8e4da" } } ], "extra": [ 1, 38, 236, 125, 132, 207, 221, 129, 253, 201, 249, 83, 3, 103, 48, 30, 167, 60, 113, 10, 2, 154, 119, 105, 250, 30, 34, 154, 200, 184, 116, 131, 114, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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