Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58577199b4b8b6d72e44fdce3486d3659221032a90ee86a38fdad564bba888d8

Tx prefix hash: e8edb18f79364060a849223fff7ab3cce5f20cf0a601bdc800db8eb43fd79f8d
Tx public key: 3c5eec9cfec7608df441ad375961f9c223f80a00981576a8a2e6a3ea42bf6966
Timestamp: 1742439937 Timestamp [UCT]: 2025-03-20 03:05:37 Age [y:d:h:m:s]: 00:069:05:58:58
Block: 1243133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49533 RingCT/type: yes/0
Extra: 013c5eec9cfec7608df441ad375961f9c223f80a00981576a8a2e6a3ea42bf6966021100000007ed95dce7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98a4669f0728ad2bcae1a4aabe3c49ed3cc7ee3f2d32b513593811dabfb4d394 0.600000000000 1730118 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": 1243143, "vin": [ { "gen": { "height": 1243133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98a4669f0728ad2bcae1a4aabe3c49ed3cc7ee3f2d32b513593811dabfb4d394" } } ], "extra": [ 1, 60, 94, 236, 156, 254, 199, 96, 141, 244, 65, 173, 55, 89, 97, 249, 194, 35, 248, 10, 0, 152, 21, 118, 168, 162, 230, 163, 234, 66, 191, 105, 102, 2, 17, 0, 0, 0, 7, 237, 149, 220, 231, 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