Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75afd3caa26729ad0729729ed89023fb49a86d7bce84ba6307be1e0d119ecb32

Tx prefix hash: cbb20fbd82c1bd2e806081b944cf659a65f5e4f1b18fb2f51cd28cd3c71d3f98
Tx public key: 65f1e90458183ec3174b4e7fe7d98bbe91b53fca505be4dcadaea63bb28d7b3c
Timestamp: 1745795559 Timestamp [UCT]: 2025-04-27 23:12:39 Age [y:d:h:m:s]: 00:206:19:45:41
Block: 1270899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145531 RingCT/type: yes/0
Extra: 0165f1e90458183ec3174b4e7fe7d98bbe91b53fca505be4dcadaea63bb28d7b3c02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbd8acf57c5de92a18b43529bc3288ea711dbd42871f3f28519e651a6ab63b0a 0.600000000000 1758144 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": 1270909, "vin": [ { "gen": { "height": 1270899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbd8acf57c5de92a18b43529bc3288ea711dbd42871f3f28519e651a6ab63b0a" } } ], "extra": [ 1, 101, 241, 233, 4, 88, 24, 62, 195, 23, 75, 78, 127, 231, 217, 139, 190, 145, 181, 63, 202, 80, 91, 228, 220, 173, 174, 166, 59, 178, 141, 123, 60, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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